Artifact: Work Order
Purpose
At the completion of iteration planning, or whenever a change is needed, the Project Manager uses the work order to turn planning into action. The work order is a negotiated agreement between Project Manager and staff to perform a particular activity or set of activities, with certain deliverables, under defined schedule, effort and resource constraints. Brief Outline
1. Identification
2. Work Breakdown Structure (WBS) identification.
3. Responsibility
4. Associated Change Requests
5. Schedule
6. Effort and other resources
7. Description of work and expected outputs.
8. Indication of agreement between Project Manager and responsible staff.
Timing
Work orders may be issued at any time the Project Manager needs to initiate work on the project. In the main this will occur at the start of an iteration (after iteration planning) and whenever an approved Change Request is passed to the Project Manager for action. The Project Manager may also use the work order to initiate problem/issue resolution work for which no Change Request is required (because it falls within the discretionary authority of the Project Manager). Responsibility
The Worker: Project Manager is responsible for the work order. Tailoring
The Work Order is the mechanism by which the Project Manager communicates
plans to project members. On small projects this could be as simple as
discussing a plan on a whiteboard and then confirming agreements through e-mail.
On large, very structured projects, perhaps some form of automated activity
management is used, where the Project Manager injects formal directions which
appear to the team members in to-do lists (maybe with some protocol for
agreement). |
Rational Unified
Process |